`:top

The `! Dynamic Invocation Interface (DII) `! is an `F33f`_`[API`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=API]`_`f which allows dynamic construction of `F33f`_`[CORBA`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=CORBA]`_`f `F33f`_`[object`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Object_(computer_science)]`_`f invocations. It is used at `F33f`_`[compile`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Compiler]`_`f time when a `F33f`_`[client`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Client_(computing)]`_`f does not have knowledge about the object it wants to invoke. With this interface an argument list is marshalled, a function is named, and a request for service is sent to the object server. DII will usually have an asynchronous mode of The following types of applications would require or benefit from DII: browsers for CORBA services, application browsers, bridges (protocol converters), applications accessing huge numbers of different interfaces, monitoring applications.

DII also provides a deferred synchronous invocation. Deferred synchronous invocations are submitted without having to wait for a response. This is similar to a one-way operation except return values and out parameters are possible, but must be `F33f`_`[polled`:/page/wikibook/entry.mu`zim=wikipedia_en_all_nopic_2025-08.zim|entry_path=Polling_(computer_science)]`_`f for.

>>External links

• http://www.cuj.com/documents/s=7981/cujcexp2007vinoski/

• https://web.archive.org/web/20041205190741/http://e-docs.bea.com/tuxedo/tux80/creclien/dii.htm#1012539

`c`F0af`_`[↑ Back to top`#top]`_`f`a